[AI Infra] Chat Experience: make Agent default in Elasticsearch Serverless and Solution view#246303
Conversation
|
Pinging @elastic/ml-ui (:ml) |
|
Pinging @elastic/appex-ai-infra (Team:AI Infra) |
| if (request) { | ||
| try { | ||
| const [, startServices] = await core.getStartServices(); | ||
| const spaces = (startServices as { spaces?: SpacesPluginStart }).spaces; |
There was a problem hiding this comment.
We can get rid of this type assertion by properly typing AIAssistantManagementSelectionPluginServerDependenciesStart in src/platform/plugins/shared/ai_assistant_management/selection/server/types.ts
There was a problem hiding this comment.
Thanks. That's definitely an improvement! Fixed here b0792c8
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
| # AI Assistant Management Selection plugin | ||
| aiAssistantManagementSelection.preferredChatExperience: 'classic' | ||
|
|
There was a problem hiding this comment.
IIUC this configuration is unnecessary as this is already the default value for the setting.
There was a problem hiding this comment.
I checked that and it's indeed redundant. Fixed here 0d42f63
It is part of a separate PR ✅ |
… unnecessary log errors before login
⏳ Build in-progress
Failed CI StepsTest Failures
History
cc @KodeRad |
| try { | ||
| const [coreStart, startServices] = await core.getStartServices(); | ||
| // Avoid security exceptions before login | ||
| const user = coreStart.security.authc.getCurrentUser(request); |
There was a problem hiding this comment.
You could also use request.auth.isAuthenticated rather than fetching the user.
I don't know which approach is preferred.
There was a problem hiding this comment.
That's good catch! I will address that in following PR
jgowdyelastic
left a comment
There was a problem hiding this comment.
Added a minor comment about not really needing to fetch the user.
but otherwise LGTM

Summary
Implements: https://github.com/elastic/ml-team/issues/1755
Follow up to: #244532
The goal of this PR is to make Chat Experience in Elasticsearch serverless/solution view default to Agent instead of Classic Assistants.
Implementation details:
serverless.es.ymlfilecoreStart.settings.client.get$<AIChatExperience>was removed as it was overriding provided configuration.Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesbackport:*labels.Identify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.